Land mobile radios and methods for operating the same

ABSTRACT

Systems and methods for operating a Land Mobile Radio (“LMR”). The methods comprise: performing Near Field Communication (“NFC”) or Radio Frequency Identification (“RFID”) operations by the LMR and an external device; and sending from the LMR or receiving at the LMR information associated with the NFC or RFID operations via the packet switched LMR infrastructure. The information associated with the NFC or RFID operations includes, but is not limited to, check-in information for an incident event, check-out information for an incident, sensor data, authentication keys, verification keys, access codes, and LMR configuration (e.g. personality) information, LMR software code, and/or LMR firmware.

BACKGROUND Statement of the Technical Field

The present disclosure relates generally to radio systems. Moreparticularly, the present disclosure relates to Land Mobile Radios(“LMRs”) and methods for operating the same.

Description of the Related Art

Public safety personnel have a method for tracking personnelaccountability during a particular public safety incident (e.g., abuilding fire) using hook and loop fasteners (e.g., Velcro®) strips.This method involves an isolated analog system (e.g., Velcro® board)that prevents information from being easily and quickly shared beyondclose proximity of the incident. No other telemetry data (e.g.,timestamp data, body sensor vital signs, environmental sensor data,etc.) is captured or recorded due to the simplicity and analog nature ofthe system. Remote resources (e.g., dispatchers, people at theheadquarters, etc.) do not have instant access to check-in data from theincident. Additionally, there is no historical record of this data afterthe incident has concluded.

As an example, when fire fighters arrive on scene of an incident (e.g.,a burning structure), they typically take a hook and loop fastener(e.g., a Velcro®) strip with their name on it and place it on awhiteboard to check-in to an incident team before entering a burningstructure. The firefighters then address the incident (e.g., enter theburning structure and put out the fire). Once the incident is resolvedor firefighters are otherwise ready to leave the incident, thefirefighters remove the hook and loop fastener (e.g., Velcro®) stripwith their name on it from the board, which signals that they have beenchecked-out of the incident.

SUMMARY

The present disclosure concerns implementing systems and methods foroperating an LMR. The methods comprise: performing Near FieldCommunication (“NFC”) or Radio Frequency Identification (“RFID”)operations by the LMR and an external device; and sending from the LMRor receiving at the LMR information associated with the NFC or RFIDoperations via the packet switched LMR infrastructure. The informationassociated with the NFC or RFID operations includes, but is not limitedto, check-in information for an incident event, check-out informationfor an incident, sensor data, authentication keys, verification keys, oraccess codes, LMR configuration (e.g., personality) information, LMRsoftware code, and/or LMR firmware.

The present solution can be used in various applications, such as fieldpersonnel management applications. In this case, present disclosureconcerns methods for operating an LMR that comprise: performing NFC orRFID operations by the LMR to check-in a field personnel member to anincident event and cause check-in information to be sent to a remotecomputing device via a packet switched LMR infrastructure or a publicnetwork; and/or performing NFC or RFID operations by the LMR tocheck-out the field personnel member from the incident event and causecheck-out information to be communicated to the remote computing devicevia the packet switched LMR infrastructure or the public network.

In some scenarios, the methods also comprise: performing NFC or ShortRange Communications (“SRCs”) operations by the LMR to pair with atleast one sensor worn by the field personnel member; periodicallyperforming SRCs by the LMR to obtain telemetry data generated by atleast one sensor paired with the LMR; and/or communicating the telemetrydata from the LMR over the packet switched LMR infrastructure.

In those or other scenarios, the methods also comprise: performing NFCoperations by the LMR to obtain access to contents of a safe box; and/orcommunicating a notification of the field personnel's access to the safebox's content from the LMR to the remote computing device via the packetswitched LMR infrastructure.

In those or other scenarios, the methods also comprise: performing NFCor RFID operations by the LMR to obtain access to an internal area of astructure that is associated with the incident event; and/or notifyingthe remote computing device of the field personnel member's access tothe internal area of the structure by the LMR via the packet switchedLMR infrastructure.

In those or other scenarios, the methods also comprises: performing NFCor RFID operations by the LMR to facilitate a detection of the LMR at apass-through inside a structure; and/or notifying the remote computingdevice of the LMR detection at the pass-through via the packet switchedLMR infrastructure.

In those or other scenarios, the methods also comprise: performing NFCor RFID operations by the LMR when the field personnel member is exitingthe structure; and/or notifying the remote computing device of the fieldpersonnel member's exiting from the structure by the LMR via the packetswitched LMR infrastructure.

The present disclosure also concerns an LMR. The LMR comprises: aprocessor configured to control operations of the LMR; a firstcommunication device coupled to the processor and configured to performNFC or RFID operations with an external device; and a secondcommunication device coupled to the processor and configured tocommunicate information over an LMR network to a packet switched LMRinfrastructure. The processor causes the second communication device tosend or receive information associated with the NFC or RFID operationsvia the LMR network. The information associated with the NFC or RFIDoperations includes, but is not limited to, check-in information for anincident event, check-out information for an incident, sensor data,authentication keys, verification keys, access codes, LMR configuration(e.g., personality) information, LMR software code, and/or LMR firmware.

The present solution can be used in various applications, such as fieldpersonnel management applications. In this case, present disclosureconcerns an LMR that comprises: a first communication device thatcommunicates information over an LMR network to a packet switched LMRinfrastructure; and a second communication device that performs NFC orRFID operations to check-in a field personnel member to an incidentevent and to cause check-in information to be sent to a remote computingdevice over the packet switched LMR infrastructure or the publicnetwork. The second communication device may also perform NFC or RFIDoperations to check-out the field personnel member from the incidentevent and to cause check-out information to be communicated to theremote computing device via the packet switched LMR infrastructure orthe public network.

In some scenarios, the second communication device may further performNFC or SRC operations to pair the LMR with at least one sensor worn bythe field personnel member. The LMR further comprises a thirdcommunication device that periodically performs SRCs to obtain telemetrydata generated by at least one sensor paired with the LMR. The telemetrydata is communicated from the first communication device of the LMR overthe packet switched LMR infrastructure.

In those or other scenarios, the second communication device furtherperforms NFC operations to obtain access to contents of a safe box. Anotification of the field personnel's access to the safe box's contentis communicated to the remote computing device via the packet switchedLMR infrastructure.

In those or other scenarios, the second communication device furtherperforms NFC or RFID operations to obtain access to an internal area ofa structure that is associated with the incident event. The firstcommunication device notifies the remote computing device of the fieldpersonnel member's access to the internal area of the structure via thepacket switched LMR infrastructure.

In those or other scenarios, the second communication device furtherperforms NFC or RFID operations to facilitate a detection of the LMR ata pass-through inside a structure. The first communication devicenotifies the remote computing device of the LMR detection at thepass-through via the packet switched LMR infrastructure.

In those or other scenarios, the second communication device furtherperforms NFC or RFID operations when the field personnel member isexiting the structure. The first communication device notifies theremote computing device of the field personnel member's exiting from thestructure by the LMR via the packet switched LMR infrastructure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present solution will be described with reference to the followingdrawing figures, in which like numerals represent like items throughoutthe figures.

FIG. 1 is a perspective view of an illustrative public safety incidentsystem.

FIG. 2 is an illustration of an illustrative architecture for a LandMobile Radio (“LMR”) shown in FIG. 1.

FIG. 3 is an illustration of an illustrative architecture for acommunication enable device.

FIG. 4 is an illustration of an illustrative architecture for acomputing device.

FIGS. 5A-5B (collectively referred to as “FIG. 5”) provide a flowdiagram of an illustrative method for managing an incident event.

FIG. 6 provides a flow diagram of an illustrative method for operatingan LMR.

FIG. 7 provides a flow diagram of another illustrative method foroperating an LMR.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments asgenerally described herein and illustrated in the appended figures couldbe arranged and designed in a wide variety of different configurations.Thus, the following more detailed description of various embodiments, asrepresented in the figures, is not intended to limit the scope of thepresent disclosure, but is merely representative of various embodiments.While the various aspects of the embodiments are presented in drawings,the drawings are not necessarily drawn to scale unless specificallyindicated.

The present solution may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the present solution is, therefore,indicated by the appended claims rather than by this detaileddescription. All changes which come within the meaning and range ofequivalency of the claims are to be embraced within their scope.

Reference throughout this specification to features, advantages, orsimilar language does not imply that all of the features and advantagesthat may be realized with the present solution should be or are in anysingle embodiment of the present solution. Rather, language referring tothe features and advantages is understood to mean that a specificfeature, advantage, or characteristic described in connection with anembodiment is included in at least one embodiment of the presentsolution. Thus, discussions of the features and advantages, and similarlanguage, throughout the specification may, but do not necessarily,refer to the same embodiment.

Furthermore, the described features, advantages and characteristics ofthe present solution may be combined in any suitable manner in one ormore embodiments. One skilled in the relevant art will recognize, inlight of the description herein, that the present solution can bepracticed without one or more of the specific features or advantages ofa particular embodiment. In other instances, additional features andadvantages may be recognized in certain embodiments that may not bepresent in all embodiments of the present solution.

Reference throughout this specification to “one embodiment”, “anembodiment”, or similar language means that a particular feature,structure, or characteristic described in connection with the indicatedembodiment is included in at least one embodiment of the presentsolution. Thus, the phrases “in one embodiment”, “in an embodiment”, andsimilar language throughout this specification may, but do notnecessarily, all refer to the same embodiment.

As used in this document, the singular form “a”, “an”, and “the” includeplural references unless the context clearly dictates otherwise. Unlessdefined otherwise, all technical and scientific terms used herein havethe same meanings as commonly understood by one of ordinary skill in theart. As used in this document, the term “comprising” means “including,but not limited to”.

The present solution concerns implementing systems and methods foroperating an LMR. The methods comprise: performing NFC or RFIDoperations by the LMR and an external device; and sending from the LMRor receiving at the LMR information associated with the NFC or RFIDoperations via the packet switched LMR infrastructure. The informationassociated with the NFC or RFID operations can include, but is notlimited to, check-in information for an incident event, check-outinformation for an incident, sensor data, authentication keys,verification keys, access codes, LMR configuration (e.g. personality)information, LMR software code, and/or LMR firmware.

The present solution can be used for personnel accountability andtracking during public safety incidents. In this case, the implementingsystems comprise LMRs including SRC enabled devices, NFC enableddevices, and/or RFID enabled devices. The NFC and/or RFID enableddevices are used by individuals to check-into and/or check-out from anincident event via a field computing device (e.g., a laptop, a tablet, asmart phone, a separate LMR device, or other mobile device).

Check-in/check-out information may be sent from the field computingdevice to a central location (e.g., dispatch center) for storage and/orprocessing. Other information may also be sent along with thecheck-in/check-out information. For example, sensor data, video, audioand/or image data is sent along with the check-in/check-out informationthat provides information about a surrounding environment (e.g., atemperature, a structure's physical state, virtualization of thesurroundings, etc.) and/or the health of the individual(s) at the timeof checking-in/checking-out. The check-in information includes, but isnot limited to, unique identifiers, check-in times and/or locationinformation (e.g., Global Positioning System (“GPS”) coordinates). Thecheck-out information includes, but is not limited to, uniqueidentifiers, check-out times and/or location information (e.g., GPScoordinates).

Although the present solution is described below in relation topersonnel accountability and tracking applications, the present solutionis not limited in this regard. The present solution can be used oremployed in any application where communication of informationassociated with NFC or RFID operations needs to be communicated to andfrom an LMR.

Illustrative System

Referring now to FIG. 1, there is provided an illustration of anillustrative public safety incident system 100. System 100 is designedto manage operations by a field personnel members 124 of public safetyand security organizations (e.g., the fire department, police departmentand/or other emergency response organizations). Each field personnelmember is assigned and provided an LMR 102 ₁, 102 ₂, . . . , 102 _(N)(collectively referred to as “102”). Similar to conventional LMRs (e.g.,the LMR disclosed in U.S. Pat. No. 8,145,262), the LMR 102 ₁, 102 ₂, . .. , 102 _(N) is configured to provide communication with other LMRsand/or a packet switched LMR infrastructure 132 via an LMR network 128and/or a cellular data network 130. The packet switched LMRinfrastructure 132 includes, but is not limited to, base stations and/orrouters. Base stations and routers are well known in the art, andtherefore will not be described herein.

However, the LMR 102 ₁, 102 ₂, . . . , 102 _(N) additionally implementsNFC technology, RFID technology, and/or SRC technology. The NFC and RFIDtechnologies facilitate communications between the LMR and a fieldcomputing device 104 for incident check-in/check-out purposes. The fieldcomputing device 104 includes, but is not limited to, an LMR, aruggedized tablet, or other incident command solution. The NFCtechnology also facilitates communication between the LMR and NFCenabled access device(s) 134 installed at access points (e.g., entrywaysor pass-through) of the structure 112 (e.g., a building, a vehicle, orwatercraft). The RFID technology also facilitates communications betweenthe LMR and/or RFID tag reader(s) 116 placed at the same or differentaccess point(s) 114 (e.g., an entryway or pass-through) of the structure(e.g., a building).

During these NFC and RFID communications, unique identifiers areprovided to the field computing device 104, NFC enabled access device(s)134, and/or RFID reader(s) 116. RFID readers are well known in the art,and therefore will not be described herein. These unique identifiers areused by the field computing device 104 and/or RFID reader(s) 116 toidentify the individual field personnel members 124 that arechecking-into an incident event, checking-out of the incident event,entering the structure, exiting the structure, and/or located inproximity to a particular pass-through or area internal to thestructure. The field computing device 104 and/or RFID reader(s) 116provide(s) the unique identifiers to one or more remote computingdevices 108, 122 along with timestamp information and/or an indicationas to whether the unique identifier is associated with a check-inaction, a check-out action, an entering action, an exiting action,and/or an internal passing through action. The remote computing devicesinclude, but are not limited to, a remote server 108 and/or computingdevice 122 (e.g., a dispatch console). The information sent from thefield computing device 104 and/or RFID reader(s) 116 is stored in adatastore 110. The information is sent from the field computing device104 via a packet switched LMR infrastructure 132 and/or a public network106 (e.g., the Internet). The information is sent from the RFIDreader(s) 116 via the public network 106.

The NFC also facilitates bi-directional communications between the LMRand safe box(es) 118 and/or other items located in, on or coupled to apart of the structure 112, and/or between the LMR and doors (not shown)and/or windows (not shown) providing access to the structure 112. Thesafe box(es) 118 include(s), but is(are) not limited to, rapid accessbox(es). A rapid access box is generally a small (possibly wall-mounted)safe that holds items (e.g., keys, access cards, access codes, medicine,etc.) that can be retrieved during emergency situations. The rapidaccess box is unlocked when it receives a unique identifier from one ofthe LMRs via an NFC communication, and verifies that the uniqueidentifier is associated with an individual that is authorized to obtainaccess to the rapid access box's contents (e.g., by comparing the uniqueidentifier to a pre-stored list of unique identifiers). Rapid accessboxes are well known in the art, and therefore will not be describedfurther herein.

The NFC further facilitates simpler pairing between the LMR andsensor(s) 126 worn by a respective field personnel member 124, ascompared to that provided by SRC technology. Still, it should be notedthat in some scenarios, SRC technology is used instead of NFC technologyto pair an LMR to sensors worn by a respective field personnel member.After a successful pairing between the LMR and sensor(s), the SRCtechnology is used for wireless communications between the paireddevices. The sensor(s) 126 include, but are not limited to, a heart ratesensor, a blood pressure sensor, a body temperature sensor, a moisturesensor, video/image camera, microphone, respiration sensor, and/or amotion sensor. The sensor data generated by the sensor(s) 126 iscommunicated to the LMR and stored in an internal memory of the LMR. TheNFC technology and/or RFID technology can be used to communicate thissensor data to an external device 108, 122 (e.g., along with thecheck-in information and/or check-out information). Alternatively oradditionally, this sensor data is communicated from the LMR using theLMR network 128 and/or the cellular data network 130.

Referring now to FIG. 2, there is provided an illustration of anillustrative architecture for an LMR 200. LMRs 102 and/or fieldcomputing device 104 of FIG. 1 are the same as or similar to LMR 200. Assuch, the discussion of LMR 200 is sufficient for understanding LMRs102, 104 of FIG. 1.

LMR 200 can include more or less components than that shown in FIG. 2 inaccordance with a given application. For example, LMR 200 can includeone or both components 208 and 210. The present solution is not limitedin this regard.

As shown in FIG. 2, the LMR 200 comprises an LMR communication device202 and a cellular data network communication device 204. Both of thesecommunication devices 202, 204 enable end-to-end LMR services in mannersknown in the art. For example, the end-to-end LMR services are achievedin the same or similar manner as that taught in U.S. Pat. No. 8,145,262.The present solution is not limited in this regard. In this way, voicedata and other data is communicated from the LMR 200 over an LMR network(e.g., LMR network 128 of FIG. 1) and/or a cellular data network (e.g.,cellular data network 130 of FIG. 1). A processor 212 and selector 214are provided to select whether the LMR network or the cellular datanetwork is to be used for communicating voice data or other data at anygiven time.

The LMR 200 also comprises an SRC enabled device 206, an NFC enableddevice 208 and/or an RFID enabled device 210. The SRC enabled device 206facilitates SRC communications. An SRC communication occurs between theLMR 200 and an external device (e.g., body worn sensors 126 of FIG. 1)over a short distance (e.g., Y feet, where Y is an integer such as ten).The SRC communication may be achieved using SRC transceivers. SRCtransceivers are well known in the art, and therefore will not bedescribed in detail herein. Any known or to be known SRC transceiver canbe used herein without limitation. For example, a Bluetooth® or Wi-Fienabled transceiver is used here. The present solution is not limited inthis regard.

The NFC enabled device 208 facilitates NFC communications. An NFCcommunication occurs between the LMR 200 and an external device (e.g.,field computing device 104 of FIG. 1 or safe box 118 of FIG. 1) over arelatively small distance (e.g., X centimeters or C inches, where C isan integer such as twelve). The NFC communication may be established bytouching the LMR 200 and the external device together or bringing themin close proximity such that an inductive coupling occurs betweeninductive circuits thereof. In some scenarios, the NFC operates at 13.56MHz and at rates ranging from 106 kbit/s to 848 kbit/s. The NFCcommunication may be achieved using NFC transceivers configured toenable contactless communication at 13.56 MHz. NFC transceivers are wellknown in the art, and therefore will not be described in detail herein.Any known or to be known NFC transceiver can be used herein withoutlimitation. In some scenarios, the NFC enabled device 208 comprises anNFC tag or maker. NFC tags and markers are well known in the art, andwill not be described herein.

The RFID enabled device 210 facilitates RFID communications. An RFIDcommunication occurs between the LMR 200 and an external device (e.g.,field computing device 104 of FIG. 1 or RFID reader 116 of FIG. 1) overrelatively short distance (e.g., W feet, where W is an integer such as30 feet). The RFID communication may be achieved using an RF antennaand/or RF transceiver. RF antennas and RF transceivers are well known inthe art, and therefore will not be described in detail herein. Any knownor to be known RF antenna and/or RF transceiver can be used hereinwithout limitation. In some scenarios, the RFID enabled device 210comprises a passive RFID tag or an active RFID tag. Both of the listedRFID tags are well known in the art, and will not be described herein.

The above-described communication components 202-210 are connected to aprocessor 212. A memory 216, display 218, user interface 222 andInput/Output (“I/O”) device(s) 220 are also connected to the processor212. During operation, the processor 212 is configured to controlselection of either the LMR communication device 202 or the cellulardata communication device 204 for providing LMR services using theselector 214. The processor 212 is also configured to collect and storedata generated by the I/O device(s) 220 and/or external devices (e.g.,body worn sensors 126 of FIG. 1). The I/O device(s) include(s), butis(are) not limited to, cameras, microphones, and/or sensors (e.g.,environmental sensors and/or motion sensors). Accordingly, the datastored in memory 216 can include, but is not limited to, images, videos,audio and/or sensor data (e.g., temperature data, moisture data, lightdata, etc.). This stored data and/or other stored data (e.g., a uniqueidentifier for the LMR 200) can be communicated from the LMR 200 via anycommunication device 202-210 in accordance with a given application.

The user interface 222 includes, but is not limited to, a plurality ofuser depressible buttons that may be used, for example, for enteringnumerical inputs and selecting various functions of the LMR 200. Thisportion of the user interface may be configured as a keypad. Additionalcontrol buttons and/or rotatable knobs may also be provided with theuser interface 222. The user interface 222 may additionally oralternatively comprise a touch screen display, and/or a microphone tofacilitate voice-activated commands.

A battery 224 is provided for powering the components 202-222 of the LMR200. The battery 224 may comprise a rechargeable and/or replaceablebattery. Batteries are well known in the art, and therefore will not bediscussed here.

Referring now to FIG. 3, there is provided an illustration of anillustrative architecture for a communication enabled device 300. TheSRC enabled device 206, NFC enabled device 208, and/or RFID enableddevice 210 of FIG. 2 is(are) the same as or similar to the communicationenabled device 300. Therefore, the discussion of communication enableddevice 300 is sufficient for understanding SRC enabled device 206, NFCenabled device 208, and/or RFID enabled device 210 of FIG. 2.

Communication enabled device 300 can include more or less componentsthan that shown in FIG. 3. However, the components shown are sufficientto disclose an illustrative embodiment implementing the presentsolution. Some or all of the components of the communication enableddevice 300 can be implemented in hardware, software and/or a combinationof hardware and software. The hardware includes, but is not limited to,one or more electronic circuits.

The hardware architecture of FIG. 3 represents an illustration of arepresentative communication enabled device 300 configured to facilitate(a) the checking-in of field personnel members to incident events, (b)the detection of when field personnel members access contents of safeboxes, (c) the detection of when field personnel members enter astructure, (d) the tracking of the field personnel member movementinside the structure, (e) the detection of when items are returned tothe safe boxes, and/or (f) the checking-out of field personnel membersfrom incident events.

The communication enabled device 300 also comprises an antenna 302 and acommunication device 304 for allowing data to be exchanged with theexternal device via SRC technology, NFC technology, and/or RFIDtechnology. The antenna 302 is configured to receive SRC, NFC and/orRFID signals from the external device and transmit SRC, NFC and/or RFIDsignals generated by the communication enabled device 300. Thecommunication device 304 may comprise an SRC transceiver, an NFCtransceiver and/or an RFID transceiver. SRC, NFC and RFID transceiversare well known in the art, and therefore will not be described herein.However, it should be understood that the SRC, NFC and/or RFIDtransceiver processes received signals to extract information therein.This information can include, but is not limited to, a request forcertain information (e.g., a unique identifier 310 and/or otherinformation 312), and/or a message including information, for example,about the health of a given individual and/or the successful access tocontents of a safe box. The communication device 304 may pass theextracted information to the controller 306.

If the extracted information includes a request for certain information,then the controller 306 may perform operations to retrieve a uniqueidentifier 310 and/or other information 312 from memory 308. The otherinformation 312 can include, but is not limited to, sensor data receivedfrom body worn sensors (e.g., sensors 126 of FIG. 1), notificationmessages from safe boxes, and/or sensor data generated by additionaloptional sensors 316 (provide with an SRC, NFC and/or RFID enableddevice) which provide information about a surrounding environment and/ormotion of the communication enabled device 300. The optional sensors 316can include, but are not limited to, temperature sensors, moisturesensors, chemical sensors, motion sensors, light sensors, smoke sensors,video/image cameras, microphones, and/or color sensors. The retrievedinformation is then sent from the communication device 304 to arequesting external device (e.g., field computing device 104 and/or RFIDreader 116 of FIG. 1).

In some scenarios, the connections between components 304, 306, 308,314, 316 are unsecure connections or secure connections. The phrase“unsecure connection”, as used herein, refers to a connection in whichcryptography and/or tamper-proof measures are not employed. The phrase“secure connection”, as used herein, refers to a connection in whichcryptography and/or tamper-proof measures are employed. Suchtamper-proof measures include enclosing the physical electrical linkbetween two components in a tamper-proof enclosure.

Notably, the memory 308 may be a volatile memory and/or a non-volatilememory. For example, the memory 308 can include, but is not limited to,a Random Access Memory (“RAM”), a Dynamic Random Access Memory (“DRAM”),a Static Random Access Memory (“SRAM”), a Read-Only Memory (“ROM”) and aflash memory. The memory 308 may also comprise unsecure memory and/orsecure memory. The phrase “unsecure memory”, as used herein, refers tomemory configured to store data in a plain text form. The phrase “securememory”, as used herein, refers to memory configured to store data in anencrypted form and/or memory having or being disposed in a secure ortamper-proof enclosure.

The components 304-316 of the communication enabled device 300 arecoupled to a power source (not shown in FIG. 3). The power source mayinclude, but is not limited to, battery or a power connection (notshown). Alternatively or additionally, the communication enabled device300 is configured as a passive device which derives power from an RFsignal inductively coupled thereto.

Referring now to FIG. 4, there is provided an illustration of anillustrative architecture for a computing device 400. Field computingdevice 104, computing device 122 and/or server 108 of FIG. 1 is(are) thesame as or similar to computing device 400. As such, the discussion ofcomputing device 400 is sufficient for understanding these component ofsystem 100.

In some scenarios, the present solution is used in a client-serverarchitecture. Accordingly, the computing device architecture shown inFIG. 4 is sufficient for understanding the particulars of clientcomputing devices and servers.

Computing device 400 may include more or less components than thoseshown in FIG. 4. However, the components shown are sufficient todisclose an illustrative solution implementing the present solution. Thehardware architecture of FIG. 4 represents one implementation of arepresentative computing device configured to provide an improved fieldpersonnel check-in, check-out and management process, as describedherein. As such, the computing device 400 of FIG. 4 implements at leasta portion of the method(s) described herein.

Some or all components of the computing device 400 can be implemented ashardware, software and/or a combination of hardware and software. Thehardware includes, but is not limited to, one or more electroniccircuits. The electronic circuits can include, but are not limited to,passive components (e.g., resistors and capacitors) and/or activecomponents (e.g., amplifiers and/or microprocessors). The passive and/oractive components can be adapted to, arranged to and/or programmed toperform one or more of the methodologies, procedures, or functionsdescribed herein.

As shown in FIG. 4, the computing device 400 comprises a user interface402, a Central Processing Unit (“CPU”) 406, a system bus 410, a memory412 connected to and accessible by other portions of computing device400 through system bus 410, a system interface 460, and hardwareentities 414 connected to system bus 410. The user interface can includeinput devices and output devices, which facilitate user-softwareinteractions for controlling operations of the computing device 400. Theinput devices may include, but are not limited, a physical and/or touchkeyboard 450, a mouse, and/or a microphone. The input devices can beconnected to the computing device 400 via a wired or wireless connection(e.g., a Bluetooth® connection). The output devices include, but are notlimited to, a speaker 452, a display 454, and/or light emitting diodes456. System interface 460 is configured to facilitate wired or wirelesscommunications to and from external devices (e.g., network nodes such asaccess points, databases, etc.).

At least some of the hardware entities 414 perform actions involvingaccess to and use of memory 412, which can be a Radom Access Memory(“RAM”), a disk driver and/or a Compact Disc Read Only Memory(“CD-ROM”). Hardware entities 414 can include a disk drive unit 416comprising a computer-readable storage medium 418 on which is stored oneor more sets of instructions 420 (e.g., software code) configured toimplement one or more of the methodologies, procedures, or functionsdescribed herein. The instructions 420 can also reside, completely or atleast partially, within the memory 412 and/or within the CPU 406 duringexecution thereof by the computing device 400. The memory 412 and theCPU 406 also can constitute machine-readable media. The term“machine-readable media”, as used here, refers to a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) that store the one or more sets ofinstructions 420. The term “machine-readable media”, as used here, alsorefers to any medium that is capable of storing, encoding or carrying aset of instructions 420 for execution by the computing device 400 andthat cause the computing device 400 to perform any one or more of themethodologies of the present disclosure.

Computing device 400 facilitates an improved field personnel check-in,check-out and management process. In this regard, computing device 400runs one or more software applications 422 for facilitating thecollection, processing and/or storage of field personnel relatedinformation and/or incident event related information. The fieldpersonnel related information includes, but is not limited to, biometricinformation, check-in status information, check-out status information,location information, video information, image information, audioinformation, and/or safe box access information. The incident eventrelated information includes, but is not limited to, locationinformation, time information, structure information, surroundingenvironment information, incident type information, field personnelon-site information, field equipment on-site information, videoinformation, image information, audio information, and/or incidentstatus information.

Illustrative Method For Managing An Incident Event

Referring now to FIG. 5, there is provided a flow diagram of anillustrative method 500 for managing an incident event. Method 500begins with 502 and continues with 504 where NFCs are optionallyperformed to pair an LMR (e.g., LMR 102 ₁, 102 ₂, . . . , or 102 _(N) ofFIG. 1) with at least one sensor (e.g., sensor 126 of FIG. 1) worn by auser of the LMR (e.g., field personnel member 124 of FIG. 1). Next in506, SRCs are optionally performed by the LMR to obtain telemetry databy the sensor(s) that were paired with the LMR in previous 504. Thetelemetry data can include, but is not limited to, heart rate data,blood pressure data, respiration data, body temperature data, moisturedata, video/image data, audio data, and/or motion data. The telemetrydata is optionally stored (at least temporarily) in an internal memory(e.g., memory 216 of FIG. 2 and/or memory 308 of FIG. 3) of the LMR, asshown by 508.

In 510, NFC or RFID communication operations are performed by the LMRand a field computing device (e.g., field computing device 104 ofFIG. 1) to check the user into an incident event (e.g., a building fireor car crash). Check-in information and/or telemetry data iscommunicated to a remote computing device (e.g., server 108 and/orcomputing device 122 of FIG. 1) from the field computing device via apacket switched LMR infrastructure (e.g., packet switched LMRinfrastructure 132 of FIG. 1) and/or a public network (e.g., publicnetwork 106 of FIG. 1). The check-in information can include, but is notlimited to, a unique identifier for the LMR, a check-in time and/or alocation of the LMR at the time of checking-in. In 514, the check-ininformation and/or telemetry data is displayed on a display (e.g.,display 454 of FIG. 4) of the remote computing device. The check-ininformation and/or telemetry data may also be stored in a datastore(e.g., datastore 110 of FIG. 1). The check-in information and/ortelemetry data is then used by the remote computing device (e.g.,dispatch console) to assist with the management of the incident event,as shown by 516. In this regard, the user (e.g., dispatcher) may inputinformation and/or commands into the remote computing device to causethe remote computing device to perform certain actions which facilitatethe management of the incident event (e.g., send messages to the LMRs offield personnel members with instructions how to handle an incidentevent and/or which field personnel members should handle and/or remainon-site of the incident event).

In optional 518, NFC operations are performed by the LMR to obtainaccess to contents of a safe box (e.g., safe box 118 of FIG. 1). The LMRthen optionally performs operations in 520 to communicate a notificationof the user's access to the contents of the safe box at the given timeand/or telemetry data to the remote computing device via the packetswitched LMR infrastructure. The notification, other data regarding theuser's access to the contents of the safe box, and/or the telemetry datamay also be stored in the datastore (e.g., datastore 110 of FIG. 1).

In optional 522, NFC or RFID communication operations are optionallyperformed by the LMR to obtain access to an internal area of a structureassociated with the incident event (e.g., structure 112 of FIG. 1). Inthis regard, the LMR communicates with an access point device (e.g.,access point device 114 of FIG. 1) of the structure. The access pointdevice can include, but is not limited to, an electro-mechanical doorlock device, an electro-mechanical window lock device, or a securitysystem device (e.g., an access card reader). In 524, the remotecomputing device is optionally notified of the user's access to theinternal area at the given time. This notification is provided by theLMR via the packet switched LMR network and/or the public network. Thenotification and/or other data regarding the user's access to theinternal area may also be stored in the datastore (e.g., datastore 110of FIG. 1). Upon completing 524, method 500 continues with optional 526of FIG. 5B.

As shown in FIG. 5B, 526 involves optionally performing NFC and/or RFIDcommunication operations by the LMR and a device installed at apass-through inside the structure (e.g., an access point device 114 ofFIG. 1 that is installed at an entrance to an internal room of thestructure). The remote computing device is optionally notified in 528 ofthe pass-through device's detection of the LMR at the pass-through. Thisnotification can be provided by the pass-through device via the publicnetwork and/or by the LMR via the packet switched LMR infrastructure.The notification and/or other data regarding the pass-through device'sdetection of the LMR at the pass-through may also be stored in thedatastore (e.g., datastore 110 of FIG. 1).

In optional 530, NFC and/or RFID communication operations are performedby the LMR and an access point device (e.g., access point device 114 ofFIG. 1) when the user is exiting the structure. The access point devicecan include, but is not limited to, an electro-mechanical door lockdevice, an electro-mechanical window lock device, or a security systemdevice (e.g., an access card reader). The remote computing device isoptionally notified in 532 of the user's exiting from the structure.This notification can be provided by the LMR via the packet switched LMRinfrastructure, and/or by the access point device via the public networkand/or the packet switched LMR infrastructure. The notification and/orother data regarding the user's exiting from the structure may also bestored in the datastore (e.g., datastore 110 of FIG. 1).

In 534, NFC or RFID communication operations are performed by the LMRand the field computing device to check the field personnel member outof the incident event. Check-out information and/or telemetry data issent from the field computing device to the remote computing device, asshown by 536. The field computing device can use the packet switched LMRinfrastructure and/or the public network in this regard. The check-outinformation can include, but is not limited to, a unique identifier forthe LMR, a check-out time and/or a location of the LMR at the time ofchecking-out. The check-out information and/or telemetry data is thendisplayed on the display of the remote computing device in 538. Thecheck-out information and/or telemetry data may also be stored in thedatastore. The check-out information and/or telemetry data is then usedby the remote computing device (e.g., dispatch console) to assist withthe management of the incident event, as shown by 540. In this regard,the user (e.g., dispatcher) may input information and/or commands intothe remote computing device to cause the remote computing device toperform certain actions which facilitate the management of the incidentevent (e.g., send messages to the LMRs of field personnel members withinstructions how to handle an incident event and/or which fieldpersonnel members should handle and/or remain on-site of the incidentevent). Subsequently, 542 is performed where method 500 ends or otherprocessing is performed (e.g., return to 502 of FIG. 5A).

Referring now to FIG. 6, there is provided a flow diagram of anillustrative method 600 for operating an LMR (e.g., LMR 102 ₁, 102 ₂, .. . , or 102 _(N) of FIG. 1). Method 600 can be absent of one or moreoperations 602-628 in accordance with a given application. Also,operations 602-628 can be performed in an order different than thatshown in FIG. 6.

Method 600 begins with 602 and continues with 604 where the LMR performsNFC or RFID operations to check-in a field personnel member (e.g., fieldpersonnel member 124 of FIG. 1) to an incident event and/or causecheck-in information to be sent to a remote computing device (e.g.,server 108 and/or computing device 122 of FIG. 1) via a packet switchedLMR infrastructure (e.g., packet switched LMR infrastructure 132 ofFIG. 1) or a public network (e.g., public network 106 of FIG. 1).

In 606, the LMR performs NFC operations to pair with at least one sensor(e.g., sensor 126 of FIG. 1) worn by the field personnel member.Thereafter in 608, the LMR periodically performs SRCs to obtaintelemetry data generated by the at least one sensor paired with the LMR.The telemetry data may also be sent from the LMR in 608 over the packetswitched LMR infrastructure.

In 610, the LMR performs NFC operations to obtain access to contents ofa safe box (e.g., safe box 118 of FIG. 1). A notification of the fieldpersonnel's access to the safe box's content is communicated from theLMR to the remote computing device via the packet switched LMRinfrastructure, as shown by 612.

In 614, the LMR performs NFC or RFID operations to obtain access to aninternal area of a structure (e.g., structure 112 of FIG. 1) that isassociated with the incident event. The LMR notifies the remotecomputing device of the field personnel member's access to the internalarea of the structure using the packet switched LMR infrastructure, asshown by 616.

In 618, the LMR performs NFC or RFID operations to facilitate adetection of the LMR at a pass-through inside the structure. The LMRnotifies the remote computing device of the LMR detection at thepass-through via the packet switched LMR infrastructure, as shown by620.

In 622, the LMR performs NFC or RFID operations when the field personnelmember is exiting the structure. The LMR notifies the remote computingdevice of the field personnel member's exiting from the structure viathe packet switched LMR infrastructure, as shown by 624.

In 626, the LMR performs NFC or RFID operations to check-out the fieldpersonnel member from the incident event and/or cause check-outinformation to be communicated to the remote computing device via thepacket switched LMR infrastructure or the public network. Subsequently,628 is performed where method 600 ends or other processing is performed.

Referring now to FIG. 7, there is provided a flow diagram of anotherillustrative method 700 for operating an LMR (e.g., LMR 102 ₁, 102 ₂, .. . , or 102 _(N) of FIG. 1). Method 700 begins with 702 and continueswith 704 where the LMR and an external device (e.g., field computingdevice 104 of FIG. 1) perform NFC or RFID operations. Next in 706,information associated with the NFC or RFID operations is sent from orreceived at the LMR via a packet switched LMR infrastructure (e.g.,packet switched LMR infrastructure 132 of FIG. 1). The information caninclude, but is not limited to, check-in information for an incidentevent, check-out information for an incident, sensor data,authentication keys, verification keys, access codes, LMR configuration(e.g. personality) information, LMR software code, and/or LMR firmware.Subsequently, 708 is performed where method 700 ends or other processingis performed (e.g., return to 702 or 704).

For example, in some scenarios, the LMR performs NFC or RFID operationswith an access point device (e.g., access point device 114 of FIG. 1) toobtain access to a structure (e.g., structure 112 of FIG. 1). Inresponse to the NFC or RFID operations, the access point devicecommunicates with a remote computing device (e.g., server 108 orcomputing device 122 of FIG. 1) to cause an authentication key,verification key and/or access code to be provided to the LMR. Thekey(s) is(are) communicated to the LMR via the packet switched LMRinfrastructure (e.g., packet switched LMR infrastructure 132 of FIG. 1).An LMR network (e.g., LMR network 128 of FIG. 1) or a cellular datanetwork 130 can be used to forward the key(s) to the LMR from the packetswitched LMR infrastructure. The present solution is not limited to theparticulars of this example.

In those or other scenarios, the LMR performs NFC or RFID operationswith a field computing device (e.g., field computing device 104 ofFIG. 1) to check-in to an incident event or check-out of an incidentevent. In response to the NFC or RFID operations, the LMR communicatescheck-in or check-out information to a remote computing device (e.g.,server 108 or computing device 122 of FIG. 1) via a packet switched LMRinfrastructure (e.g., packet switched LMR infrastructure 132 of FIG. 1).An LMR network (e.g., LMR network 128 of FIG. 1) or a cellular datanetwork 130 can be used to facilitate this communication of check-in orcheck-out information. The present solution is not limited to theparticulars of this example.

In those or other scenarios, the LMR performs NFC or RFID operationswith a device that has shareable LMR configuration information, LMRsoftware, and/or LMR firmware (e.g. a second LMR 102 in FIG. 1), or arepository device that stores a plurality of LMR configurations/softwarecode/firmware code) in order to update the LMR with a new/modifiedconfiguration, software code, and/or firmware code. In response to theNFC or RFID operations between the LMR and the second device, the LMRcommunicates with a remote computing device (e.g., server 108 orcomputing device 122 of FIG. 1) to obtain authorization from the remotecomputing device to proceed with exchanging configuration/softwarecode/firmware code between the two NFC/RFID devices. Alternatively or inaddition to that, the LMR may communicate with a remote computing device(e.g., server 108 or computing device 122 of FIG. 1) to obtainadditional configuration/software code/firmware from the remotecomputing device. Using the configuration, software, and/or firmwareinformation found on LMR, second device, and/or remote computing device,the LMR is updated with the desired new/modified configuration, softwarecode, and/or firmware code, and/or the second device is updated with thedesired new/modified configuration, software code, and or firmware code.An LMR network (e.g., LMR network 128 of FIG. 1) or a cellular datanetwork (e.g., cellular data network 130 of FIG. 1) can be used tofacilitate this communication of LMR configuration/software/firmwareinformation. The present solution is not limited to the particulars ofthis example.

Although the present solution has been illustrated and described withrespect to one or more implementations, equivalent alterations andmodifications will occur to others skilled in the art upon the readingand understanding of this specification and the annexed drawings. Inaddition, while a particular feature of the present solution may havebeen disclosed with respect to only one of several implementations, suchfeature may be combined with one or more other features of the otherimplementations as may be desired and advantageous for any given orparticular application. Thus, the breadth and scope of the presentsolution should not be limited by any of the above describedembodiments. Rather, the scope of the present solution should be definedin accordance with the following claims and their equivalents.

What is claimed is:
 1. A method for operating a Land Mobile Radio(“LMR”), comprising: performing, by the LMR, Near Field Communication(“NFC”) or Radio Frequency Identification (“RFID”) operations to atleast register a field personnel member at a given site of an incidentevent; responsive to the NFC or RFID operations, communicating from theLMR to a remote computer device (i) a time at which registration of thefield personnel member at the given site occurred, and (ii) a requestfor authorization to exchange LMR software with a device that isassociated with another field personnel member who is also registered atthe given site; and responsive to said registration and saidauthorization, performing the following operations by the LMR: exchangeLMR software with the device; and modify operations in accordance withthe LMR software to facilitate management of the incident event as theincident event is being subsequently addressed by at least the fieldpersonnel member.
 2. The method according to claim 1, wherein the LMRalso communicates check-out information for an incident, authenticationkeys, verification keys, and access codes.
 3. A Land Mobile Radio(“LMR”), comprising: a processor configured to control operations of theLMR; a first communication device coupled to the processor andconfigured to perform Near Field Communication (“NFC”) or RadioFrequency Identification (“RFID”) operations to at least register afield personnel member at a given site of an incident event; and asecond communication device coupled to the processor and configured tocommunicate information over an LMR network to a packet switched LMRinfrastructure; and wherein the processor causes the secondcommunication device to send or receive information via the LMR networkto or from a remote computer device, the information comprising (i) atime at which registration of the field personnel member at the givensite occurred and (ii) a request for authorization to exchange LMRsoftware with another device that is associated with another fieldpersonnel member who is also registered at the given site of theincident event; and wherein the processor causes the LMR to perform thefollowing operations responsive to the registration and theauthentication: exchange at least one of LMR software with the anotherdevice; and modify operations in accordance with the LMR software tofacilitate management of the incident event as the incident event issubsequently being addressed by at least the field personnel member. 4.The LMR according to claim 3, wherein the processor further causes thefirst or second communication device to at least one of check-ininformation for an incident event, check-out information for anincident, an authentication key, a verification key, and an accesscodes.
 5. A method for operating a Land Mobile Radio (“LMR”),comprising: performing Near Field Communication (“NFC”) or RadioFrequency Identification (“RFID”) operations by the LMR to check-in afield personnel member into an incident event, and to cause informationto be sent to a remote computing device via a packet switched LMRinfrastructure or a public network for reporting a presence of the fieldpersonnel member at a given site to a public safety and securityorganization, the information comprising a check-in time specifying atime (i) at which the field personnel member was registered at alocation of the incident event and (ii) that occurred prior to when thefield personnel member began addressing the incident event, and arequest for authorization to exchange code with another device that isregistered at the given site at a same time as the LMR; and receiving bythe LMR at least one of LMR configuration information, LMR software codeand LMR firmware which was transmitted from the another device inresponse to a registration of the field personnel member at the givensite and an authorization for the LMR and the another device to exchangesaid code with each other.
 6. The method according to claim 5, furthercomprising performing NFC or RFID operations by the LMR to check-out thefield personnel member from the incident event and cause check-outinformation to be communicated to the remote computing device via thepacket switched LMR infrastructure or the public network.
 7. The methodaccording to claim 5, further comprising performing NFC operations bythe LMR to pair with at least one sensor worn by the field personnelmember.
 8. The method according to claim 5, further comprisingperiodically performing Short Range Communications (“SRCs”) by the LMRto obtain telemetry data generated by at least one sensor paired withthe LMR.
 9. The method according to claim 8, further comprisingcommunicating the telemetry data from the LMR over the packet switchedLMR infrastructure.
 10. The method according to claim 5, furthercomprising performing NFC operations by the LMR to obtain access tocontents of a safe box.
 11. The method according to claim 10, furthercomprising communicating a notification of the field personnel's accessto the safe box's content from the LMR to the remote computing devicevia the packet switched LMR infrastructure.
 12. The method according toclaim 10, further comprising performing NFC or RFID operations by theLMR to obtain access to an internal area of a structure that isassociated with the incident event.
 13. The method according to claim12, further comprising notifying the remote computing device of thefield personnel member's access to the internal area of the structure bythe LMR via the packet switched LMR infrastructure.
 14. The methodaccording to claim 5, further comprising performing NFC or RFIDoperations by the LMR to facilitate a detection of the LMR at apass-through inside a structure.
 15. The method according to claim 14,further comprising notifying the remote computing device of the LMRdetection at the pass-through via the packet switched LMRinfrastructure.
 16. The method according to claim 5, further comprisingperforming NFC or RFID operations by the LMR when the field personnelmember is exiting the structure.
 17. The method according to claim 16,further comprising notifying the remote computing device of the fieldpersonnel member's exiting from the structure by the LMR via the packetswitched LMR infrastructure.
 18. A Land Mobile Radio (“LMR”),comprising: a first communication device that communicates informationover an LMR network to a packet switched LMR infrastructure; and asecond communication device that performs Near Field Communication(“NFC”) or Radio Frequency Identification (“RFID”) operations tocheck-in a field personnel member into an incident event, and to causeinformation to be sent to a remote computing device over the packetswitched LMR infrastructure or the public network for reporting apresence of the field personnel member at a given site of the incidentevent to a public safety and security organization, the informationcomprising a check-in time specifying a time (i) at which the fieldpersonnel member was registered at a location of the incident event and(ii) that occurred prior to when the field personnel member beganaddressing the incident event, and a request for authorization toexchange software code with another device that is registered at thegiven site at a same time as the LMR; wherein the first communicationdevice exchanges at least one of LMR configuration information, LMRsoftware code and LMR firmware with the another device in response to acheck-in of the field personnel member at incident event and anauthorization for the LMR and the another device to exchange code witheach other.
 19. The LMR according to claim 18, wherein the secondcommunication device further performs NFC or RFID operations tocheck-out the field personnel member from the incident event and tocause check-out information to be communicated to the remote computingdevice via the packet switched LMR infrastructure or the public network.20. The LMR according to claim 18, wherein the second communicationdevice further performs NFC operations to pair the LMR with at least onesensor worn by the field personnel member.
 21. The LMR according toclaim 18, further comprising a third communication device thatperiodically performs Short Range Communications (“SRCs”) to obtaintelemetry data generated by at least one sensor paired with the LMR. 22.The LMR according to claim 21, wherein the telemetry data iscommunicated from the first communication device of the LMR over thepacket switched LMR infrastructure.
 23. The LMR according to claim 18,wherein the second communication device further performs NFC operationsto obtain access to contents of a safe box.
 24. The LMR according toclaim 23, wherein the first communication device further communicates anotification of the field personnel's access to the safe box's contentto the remote computing device via the packet switched LMRinfrastructure.
 25. The LMR according to claim 18, wherein the secondcommunication device further performs NFC or RFID operations to obtainaccess to an internal area of a structure that is associated with theincident event.
 26. The LMR according to claim 25, wherein the firstcommunication device further notifies the remote computing device of thefield personnel member's access to the internal area of the structurevia the packet switched LMR infrastructure.
 27. The LMR according toclaim 18, wherein the second communication device further performs NFCor RFID operations to facilitate a detection of the LMR at apass-through inside a structure.
 28. The LMR according to claim 27,wherein the first communication device further notifies the remotecomputing device of the LMR detection at the pass-through via the packetswitched LMR infrastructure.
 29. The LMR according to claim 18, whereinthe second communication device further performs NFC or RFID operationswhen the field personnel member is exiting the structure.
 30. The LMRaccording to claim 29, wherein the first communication device furthernotifies the remote computing device of the field personnel member'sexiting from the structure by the LMR via the packet switched LMRinfrastructure.